Allow explicit local dataset paths#361
Draft
MaxGhenis wants to merge 1 commit into
Draft
Conversation
MaxGhenis
force-pushed
the
allow-unmanaged-local-datasets
branch
from
deda9e1 to
6ee5d14
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
resolve_managed_dataset_referenceto accept explicit local.h5paths only whenallow_unmanaged=TrueWhy
The local pipeline and long-run dataset workflows need a deliberate escape hatch for locally built datasets. Without this, local validation has to route through the bundled release manifest even when the caller explicitly wants to test a local H5.
Validation
uv run --extra dev python -m pytest tests/test_release_manifests.py -q